The 7am Task Still Runs With The Laptop Shut. It Just Cannot Read Your Folder.
This is a well-built card. Five layers down a coloured spine: a folder, then three files — about-me.md, writing-style.md, my-company.md — and then two scheduled tasks at 7am and 5pm. The subtitle states the payoff plainly:
“One folder, three files, two schedules. Claude starts every day already briefed.”
Layers one to four build the brief. Layer five is when it gets read. And layer five is where the architecture has a condition on it that the card does not mention.
Source card: “Build a one-person company using Claude Cowork” — BANI Academy, 21 October 2026. Home layer, identity layer, voice layer, goal layer, routine layer.
View the original post on Facebook
When a scheduled task can read your folder
From the support article on using Cowork across web, desktop and mobile:
A cloud session can read and write files in folders you have connected on your computer “only while the desktop app is open on that computer”, and where the session “was started on desktop or is a scheduled task”.
“If the app is closed, the session keeps running but can’t reach your local files.”
So a Cowork scheduled task is explicitly allowed to touch your connected folders — that part works. The condition is that the desktop app has to be open on the machine the folder is on. Close the laptop before bed and the 7am task does not fail. It runs. It simply runs without the four layers underneath it.
Diagram: where each layer lives, and whether 7am can see it
| Layer | Where it lives | Reachable by the 7am task if the app is closed? |
|---|---|---|
1 · Folder — ~/Claude Cowork/ |
Your disk | No. “Can’t reach your local files” |
2 · Identity — about-me.md |
In that folder | No |
3 · Voice — writing-style.md |
In that folder | No — so the banned-words list does not apply to the drafted replies |
4 · Goals — my-company.md |
In that folder | No — so “reads top 3 goals” does not happen |
| 5 · Routine — 7am and 5pm | Scheduled, cloud-side | Yes — it runs. That is the whole problem |
The failure mode is a brief, not an error
This is the part worth sitting with. A task that cannot reach a file it needs does not necessarily stop. The documentation’s phrasing is precise and a little unnerving: “the session keeps running but can’t reach your local files”.
So at 7am you get what the card promises — emails sorted, replies drafted — written by a model that has never read who you are, what you sell, or which four phrases you banned. It will be competent. It will sound like nobody in particular. And nothing in the output says “I could not open about-me.md”, because from the model’s side there was no file to miss.
That is the same shape as the one the card’s own voice layer is built to prevent. writing-style.md exists to stop drafts sounding generic — and the one moment it is guaranteed not to apply is the automated one that writes without you watching.
Three fixes, and the article names two of them
| Fix | What it costs | When to pick it |
|---|---|---|
| Leave the desktop app open and the machine awake | A machine that does not sleep | Simplest. If you have a desktop that stays on, the card works exactly as drawn with nothing changed |
| Move the three files out of the folder and into a Project | Ten minutes, once | The structural fix. A Project is held by your Claude account rather than your disk, so a scheduled task reaches it whatever the laptop is doing |
| Use Claude Code for the work that must stay local | A different surface | The article’s own recommendation for “tasks that run only on your computer”. It also gives a migration path: download the task data, unzip, open the folder in Claude Code and run /port-task-data |
| Leave it and accept an un-briefed 7am | Nothing | Defensible if the 7am job is pure triage — sorting mail does not need your voice. The 5pm wrap-up is the one that needs the goals file |
That second row deserves one more line, because it resolves something neatly. A month before this card, the same page published ten Cowork tips whose third was “A Skill is a command. A Project is a place for files.” That is the cleanest definition of the pair we have read — and it is the answer to this card’s problem. Files that a schedule must read belong in the place your account holds, not the place your disk holds.
What the card gets right, which is most of it
| Layer | The idea | Verdict |
|---|---|---|
| 1 · One folder, three subfolders | “One place Claude reads before you type. No more pasting your background” | Sound, with the caveat above. About Me / Outputs / Templates is a sensible minimum shape |
| 2 · Let Claude interview you | “Don’t write it yourself… ask for 20 questions… answer out loud” | The best idea on the card. People write flat self-descriptions and speak vivid ones. “Q1: Who pays you, and for what result?” is a better opening question than most consultants manage |
| 3 · A banned-words file | “leverage”, “delve”, em dashes, “hope this finds you” | The highest-leverage item here, and the most testable. A ban list is a constraint you can check was obeyed, unlike “write in my voice” |
| 4 · Five minutes every Monday | Rewrite the top three priorities, then use one prompt shape | Good. The weekly rewrite is what stops the goals file going stale, which is the failure mode of every such file |
| 5 · Two schedules | “Tonight’s log is tomorrow’s brief” | The right idea — a closing loop beats a to-do list. Just make sure it can read the files |
One note on the card from a month earlier
Readers who follow the same page will have noticed that this card and the ten Cowork tips from September give opposite instructions on the same three objects. That card says “Delete your .md folders” and “Delete your about-me file”; this one says build a folder of .md files and have Claude interview you for an about-me.
Both are defensible and the resolution is not a compromise. Standing context helps when it is short, current and about you, and hurts when it is long, stale and about a project you finished. The September card is describing the second case; this one is describing the first — which is why its layer 4 insists on five minutes every Monday. A file you rewrite weekly is not the file the other card wants deleted.
Four honest caveats
- We did not build the setup. This is the card checked against the Cowork support article in October 2026. If your scheduled task does read the folder with the app closed, the article has changed and you should trust your own machine over this page.
- “Connected folders” is doing work in that quotation. The condition applies to folders you connected on a computer. Files held by your Claude account are a different thing, which is exactly why the Project route fixes it.
- Cowork moves faster than most of what we check. The card’s own fine print says so: “Cowork features and scheduling change often and may depend on your plan.”
- This is a good card. The interview trick and the banned-words file are two of the better ideas we have taken apart this month, and the five-layer shape is genuinely how a sole operator should think about it. The objection is one line of plumbing, not the design.
The one-line version
Four of the five layers live on your disk and the fifth lives in the cloud, and the documentation says a scheduled task reaches your folders only while the desktop app is open — so the 7am brief arrives on time, every time, and on the mornings you shut the laptop it arrives knowing nothing about you.
Put the three files in a Project, or leave the app running. Then “already briefed” is true on the mornings it matters.
Source card: “Build a one-person company using Claude Cowork” — BANI Academy, 21 October 2026.
View the original post on Facebook · Related: the three schedulers, and which one sees your files
